Skip to main content Skip to complementary content
Qlik Resources

Limitations and considerations

The following section describes the limitations of using Microsoft Azure Synapse Analytics as a Replicate target.

  • Source columns with CHAR/VARCHAR data types and a non-Latin collation (e.g. "Chinese_PRC_CI_AS") need to be mapped to NVARCHAR. This can be done by defining a global transformation for all tables in the replication task or by defining a single transformation for a specific table.

    For more information on defining transformations, see Starting the Global Transformation Rules wizard and Defining transformations for a single table/view.

  • Empty source column handling:

    • When using the Polybase load method, an empty value in a source text column (for example VARCHAR or CLOB) will be inserted as a space into the corresponding target column. Therefore, if you need empty values in source text columns to be inserted as empty values into the corresponding target columns, use the COPY Statement load method instead.

      For more information on the loading options, see Setting general connection properties.

    • When replicating a source binary column (for example, VARBINARY or BLOB) with an empty value, Replicate inserts a NULL into the corresponding target column.

    Information noteEmpty values are not NULL, but data with zero length.

  • The rename column DDL is not supported.

  • Blob storage is not supported when Qlik Replicate is installed on Linux.
  • Full LOB replication is not supported.
  • Replication of records exceeding 1 MB is not supported.
  • Replication of data with 4-byte emoji characters requires the data type to be a wide string (for example, NCHAR/NVARCHAR/NCLOB) on the target.

  • When PolyBase is selected as the Load data using method, the characters \r and \n in the data are replaced with a space. For new line support, you must select COPY Statement as the Load data using method.

    See also: Setting general connection properties.

Change processing (CDC) limitations

  • Capture of BLOB column changes exceeding 2000 bytes is not supported
  • Capture of CLOB/NCLOB column changes exceeding 4000 bytes is not supported

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here